feat(quart): Add span streaming support to Quart integration - #6502

We'll need a streaming counterpart for this piece of code, something like:

client = sentry_sdk.get_client()

if has_span_streaming_enabled(client.options):
    span = get_current_span()
    if span is not None:
        span._segment._update_active_thread()

Missing MySQL host env variable

Medium Severity

The DB CI job sets SENTRY_PYTHON_TEST_POSTGRES_HOST to postgres for Python 3.6/3.7 container runs but does not set SENTRY_PYTHON_TEST_MYSQL_HOST the same way for the new MySQL service. tests/integrations/aiomysql reads that variable and defaults to localhost, which is unreachable from the job container network.

 

^{Reviewed by Cursor Bugbot for commit dde12e6. Configure here.}

I don't know where this came from 🤔

Missing MySQL host container env

Medium Severity

The new MySQL CI env sets SENTRY_PYTHON_TEST_MYSQL_USER and password but not SENTRY_PYTHON_TEST_MYSQL_HOST. For Python 3.6/3.7 jobs that run inside a service-linked container, tests/integrations/aiomysql defaults to localhost, unlike Postgres and Redis which use the mysql service hostname in that layout.

 

^{Reviewed by Cursor Bugbot for commit e5eb0b3. Configure here.}

These should be set in user_properties instead, like ip_address is -- if they're set on the scope via set_user, they'll be set on all spans (including the segment) automatically

The client.address didn't appear on the list of common attribute keys which is why I didn't add it (not sure if this is potentially a mistake?) but at the very least I can clean up lines 218-220 since it's being added on the scope.

If we want to merge like this, this should interact with the isolation scope. The top-level set_user API sets the user on the isolation scope, so if there is any user data set by the user, it'll be on the isolation scope.

Sounds good! I realized looking at this again that there's a reference to the isolation scope above so I'll use that here.

Quart auth access unguarded

Medium Severity

Replacing _add_user_to_event with _get_current_user_id_from_quart drops the prior capture_internal_exceptions guard around reading quart_auth.current_user. In the span-streaming request_started path that helper runs outside any internal-exception handler, so a misconfigured or broken Quart Auth accessor can abort request startup instead of being ignored like before.

 

^{Reviewed by Cursor Bugbot for commit 6411bda. Configure here.}